5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
- Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-8: Runtime Subroutine's and Predefined Processes

.UTIL CLEAR PASS LIST


This subroutine clears any unfilled PASS requests.

Usage:

Description:

This subroutine clears any unfilled PASS requests. No parameters are required.

This can be useful if you have issued a number of PASS statements, but decide not to run the subroutine. This will remove the unused values, otherwise they will remain until the next subroutine is invoked.

A common situation is where you have PASS statements in the Pre-Invocation of an Optional or Automatic child. This event point may execute more than once before the child is actually executed, so you may want to use this subroutine before the PASS statements to clear any that were executed previously. Note that it's possible for the Pre-Invocation point to execute without the child process ever executing, therefore if you are going to put PASS statements in the Pre-invocation event point, it's a good idea to condition them on --- OPTION being equal to the Optional Child in question. This cannot be done in Automatic Children, so PASS statements should be avoided in that event point, if possible. If you must use them, use this subroutine to clear any unused PASSed values.

Application Design Manual                                         "Powered by Appx Software"

1173

©2006 By APPX Software, Inc. All Rights Reserved